ci: nightly hardware-attached bring-up workflow scaffold (#696)#710
Conversation
#696. Scaffolds the workflow + per-board fingerprint files + setup docs so registering a self-hosted runner with the hw-ci label is the only remaining step to activate hardware CI. What ships: - .github/workflows/hw-ci.yml — schedule (nightly 02:30 UTC) + PR hw-ci-label trigger + workflow_dispatch. runs-on: [self-hosted, hw-ci]; double-guarded with an 'if:' that skips when no runner is registered. Matrix per board family (esp32s3 / lpc845brk / pico / teensy41 / samd51) with fail-fast off so a single-board hardware fault doesn't mask the others. 'Detect attached hardware' step consults tests/hw/fingerprints/<board>.txt and skips with a warning when none of the listed VID:PIDs are present. Deploy + bring-up steps run only when hardware is detected. On nightly cron failure, opens or updates an hw-ci-failure label issue with the run URL. - tests/hw/README.md — fixture-layout convention + 'adding a new board family' recipe. - tests/hw/fingerprints/README.md + per-board .txt files (esp32s3, lpc845brk, pico, teensy41, samd51) — VID:PID-per-line presence checks. Pulled from the same BOARD_FINGERPRINTS table the runtime serial-probe CLI uses, so the two stay in sync. - agents/docs/hardware-ci-setup.md — runner-registration recipe, udev rules, first-run validation steps. Out of scope (operational): - Registering the runner itself (hardware + GitHub UI step, not source). - Per-board known-good firmware blobs (committed once the boards are wired in; tests/hw/README.md documents the known_good_<board>.{bin,elf,uf2} layout). Closes #696.
|
Warning Review limit reached
More reviews will be available in 42 minutes and 6 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
#696. Scaffolds the workflow + per-board fingerprint files + setup docs so registering a self-hosted runner with the
hw-cilabel is the only remaining step to activate hardware CI.What ships
.github/workflows/hw-ci.yml— schedule (nightly 02:30 UTC) + PRhw-cilabel trigger + workflow_dispatch. Matrix per board family (esp32s3 / lpc845brk / pico / teensy41 / samd51) with fail-fast off so a single-board hardware fault doesn't mask the others. "Detect attached hardware" step consultstests/hw/fingerprints/<board>.txtand skips with a warning when no listed VID:PID is present. On nightly cron failure, opens or updates anhw-ci-failurelabel issue with the run URL.tests/hw/README.md— fixture-layout convention + "adding a new board family" recipe.tests/hw/fingerprints/README.md+ per-board.txtfiles (esp32s3, lpc845brk, pico, teensy41, samd51) — VID:PID-per-line presence checks. Pulled from the sameBOARD_FINGERPRINTStable the runtime serial-probe CLI uses.agents/docs/hardware-ci-setup.md— runner-registration recipe, udev rules, first-run validation steps.Out of scope (operational, not source)
tests/hw/README.md).Closes #696.